Conversation
ghost
assigned
| ipld-ns, namespace, 0xe2, IPLD path | ||
| ipfs-ns, namespace, 0xe3, IPFS path | ||
| swarm-ns, namespace, 0xe4, Swarm path | ||
| ECDSA, multihash, 0xec, ECDSA signature |
There was a problem hiding this comment.
This wouldn't be a multihash, it would be a signature. So we're on the same page, how are you planning on using this codec to identify ECDSA signatures?
There was a problem hiding this comment.
do we have plans on doing a “multisign” at some point?
There was a problem hiding this comment.
We do but it's unclear how this should look. The signature algorithm is usually a property of the key, not the signature, and libp2p actually has an ECDSA key type.
There was a problem hiding this comment.
I'm working on clojure implementation of multisig and multikey.
Multikey is for expressing public keys and would look like this: algo+length+x509encodedKey
Where algo is ecdsa, rsa, or other, length is length of x509encodedKey.
Multisig is for expressing signatures and would look like this: algo+length+signatureBytes
Where algo could be sha256-with-ecdsa.
Unlike with multihashes, it would not be possible to compare payloads for equality (as signature may be different for the same data each time the signature is calculated), but having a public key it would still be possible to verify the signature.
There was a problem hiding this comment.
IMO, ECDSA is a bit too generic. For example, how do you distinguish between secp256k1 and r1?
There was a problem hiding this comment.
Do you still need curve params if you have x509encodedKey as part of multikey?
5 participants
Elliptic Curve Digital Signature Algorithm or ECDSA is a cryptographic algorithm used by many most?) blockchains to sign data.
Would love to use multicodec for my work with the BSV blockchain so please have a look at toe one line PR.